5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
- Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-2: True/False Status Indicators

Using Hyphens as Placeholders


There may be cases where you want to unconditionally execute a statement without checking one or more existing status indicator values, while preserving the state of that indicator level. To accomplish this action, you can use a '-' (hyphen) as a placeholder within the true/false execution conditions. For example:

          IF   TAR WORK FLAG  EQ 1
    -     IF   TAR RECEIPT1 POST STARTED  EQ 1

In this example, the first IF statement executes unconditionally and sets the level 1 internal true/false status indicator to T or F. The second IF has a '-' in the first position of its execution conditions so it also executes unconditionally, setting the level 2 internal true/false status indicator (level 2 corresponds to the leftmost execution condition with a blank value). You can now execute additional statements conditionally based on the first two levels, which can be TT, TF, FT, or FF. This type of ?truth table? logic can be extended to additional levels.

For instance, you can perform a three-statement series as shown in the following example, and then check for internal true/false status indicator values of TTT, TTF, TFT, TFF, FTT, FTF, FFT, or FFF.

          IF   TAR WORK FLAG      EQ 1
    -     IF   TAR RECEIPT1 POST STARTED  EQ 1
    --    IF   TAR POST ERRORS    GT 0

Application Design Manual                                         "Powered by Appx Software"

526

©2006 By APPX Software, Inc. All Rights Reserved